Systems and methods for dynamic audiovisual conferencing in varying network conditions

ABSTRACT

Embodiments described herein provide for the dynamic adjustment of traffic associated with audiovisual conferences or other types of communication sessions in situations where a network connection of one or more conference participants exhibits issues that may affect audio and/or video quality. The adjustment may include the determination at a particular conference participant (e.g., a particular User Equipment (“UE”)) of degraded network conditions, the generation of condensed conference information at the UE, and the outputting of the condensed conference information via the network. The condensed conference information may be included in control signaling. The condensed conference information may be used to generate reconstructed conference information, which may be distributed to other conference participants.

BACKGROUND

Wireless user equipment (“UE”), such as mobile telephones or otherwireless communication devices, may participate in voice calls,audiovisual conferences, or the like via one or more networks, such as aLocal Area Network (“LAN”), the Internet, or other networks.Communications via such networks may experience issues, such asincreased latency, increased jitter, reduced throughput, or the like,which may affect audio or video quality.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 illustrate an example overview of one or more embodimentsdescribed herein;

FIGS. 3 and 4 illustrate an example of generating and using models togenerate reconstructed and/or extrapolated conference information basedon condensed conference information, in accordance with someembodiments;

FIG. 5 illustrates an example process for generating and providingcondensed conference information based on the detection of degradednetwork conditions, in accordance with some embodiments;

FIG. 6 illustrates an example environment in which one or moreembodiments, described herein, may be implemented;

FIG. 7 illustrates an example arrangement of a radio access network(“RAN”), in accordance with some embodiments; and

FIG. 8 illustrates example components of one or more devices, inaccordance with one or more embodiments described herein.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

Embodiments described herein provide for the dynamic adjustment and/orenhancement of traffic associated with voice calls, audiovisualconferences, and/or other types of communication sessions (referred toherein as “conferences” for the sake of brevity), in situations where anetwork connection of one or more conference participants exhibitsissues that may affect audio and/or video quality. As discussed herein,the adjustment and/or enhancement may include the determination ofdegraded network conditions at a particular conference participant(e.g., a particular User Equipment (“UE”)), the generation of condensedconference information, and the transmission of the condensed conferenceinformation to a Dynamic Conferencing System (“DCS”) of someembodiments. The condensed conference information may be transmitted inlieu of “full” conference information, such as audio and/or video. Thecondensed conference information may include, for example, a texttranscription of speech received at the UE (e.g., as uttered by a userof the UE), and may thus consume less network bandwidth than audioand/or video data that may be captured by the UE and provided to otherconference participants under “normal” network conditions (e.g., whenthe network conditions have not degraded to below a threshold quality).

In some embodiments, the condensed conference information may be encodedin, or otherwise included in, control signaling associated with theconference. Control signaling may, in some embodiments, be associatedwith a higher priority communication channel than user plane traffic,such as audio data, video data, etc. associated with the conference. Assuch, the condensed conference information may be communicated usinghigh priority Quality of Service (“QoS”) parameters, to ensurelow-latency handling of such information. As further described below,the condensed conference information may be used to generatereconstructed and/or extrapolated conference information, to simulatethe speech and/or video of a user of the UE, to minimize disruptionsthat may be otherwise caused by network issues that affect connectionassociated with the UE. For example, the DCS of some embodiments maygenerate and/or utilize one or more models associated with the UE and/ora user of the UE to generate or simulate speech and/or video of the userbased on the condensed conference information, in order to furtherenhance the simulated speech and/or video of the user. In someembodiments, the DCS may be implemented by a Multi-Access/Mobile EdgeComputing (“MEC”) device, referred to sometimes herein simply as a“MEC,” which may include relatively robust processing resources at anedge of a network, thus further enhancing the speed at which thereconstructed and/or extrapolated conference information may begenerated. As such, the reconstructed and/or enhanced conferenceinformation may be provided to other participants in real time ornear-real time, thus minimizing disruptions to the conference.

As shown in FIG. 1 , for example, a set of UEs 101-1, 101-2, and 101-3(sometimes referred to herein individually as “UE 101” or collectivelyas “UEs 101”) may participate in an audiovisual conference, in whichvideo data (e.g., depicting users' faces) and audio data (e.g.,including users' speech) may be received from and distributed to UEs101. For example, UEs 101 may communicate with DCS 103 via network 105,in order to send and/or receive control signaling 107 and/or user planetraffic 109 associated with the conference.

DCS 103 may be, may include, and/or may be implemented by one or moredevices or systems, such as a web server, an application server, and/orsome other type of network-accessible resource. In some embodiments, DCS103 may be, may include, and/or may be implemented by a MEC that isdeployed at a network edge, such as at or communicatively coupled to abase station of a radio access network (“RAN”) of a wireless network. Insome embodiments, some functions of DCS 103 may be performed by acloud-based device or system that is accessible via the Internet or oneor more other networks, while other functions of DCS 103 may beperformed by a MEC or other type of edge resource that is accessible viaa RAN of a wireless network.

Control signaling 107 may include messages such as conference setupmessages, messages related conference features (e.g., hold, addparticipant, block participant, mute participant, etc.), and/or othertypes of control messages. In some embodiments, control signaling 107may include Session Initiation Protocol (“SIP”) messages and/or messagesassociated with some other suitable protocol. In some embodiments, userplane traffic 109 may include video traffic, audio traffic, and/or othertypes of traffic associated with the conference. In some embodiments,control signaling 107 and user plane traffic 109 may be associated withdifferent QoS parameters. For example, control signaling 107 may, insome embodiments, be associated with a higher QoS level than user planetraffic 109. In some embodiments, control signaling 107 may beassociated with a QoS level that allows or guarantees a lower maximumthroughput than user plane traffic 109. For example, while user planetraffic 109 may be associated with a relatively high maximum orguaranteed throughput to allow for video traffic, audio traffic, orother types of traffic that may consume a relatively high amount ofbandwidth, control signaling 107 may be associated with a relatively lowmaximum or guaranteed throughput to allow for text-based communicationssuch as protocol messages, keep-alive or “heartbeat” messages, commands,metadata, etc. In some embodiments, control signaling 107 may becommunicated between respective UEs 101 and DCS 103 via one or morecontrol plane communication channels, and user plane traffic 109 may becommunicated between respective UEs 101 and DCS 103 via one or more userplane communication channels.

Based on control signaling 107 from one or more UEs 101, DCS 103 mayperform and/or otherwise facilitate (at 102) a setup of a conferencebetween UEs 101-1, 101-2, and 101-3. For example, a particular UE 101may communicate (e.g., via control signaling 107) with DCS 103 toinitiate the conference, and other UEs 101 may communicate with DCS 103(e.g., via control signaling 107) to join the conference. UEs 101 mayfurther communicate with DCS 103 (e.g., via user plane traffic 109) tosend and/or receive conference user plane traffic, such as audio and/orvideo. For example, a user of UE 101-1 may speak into an audio inputdevice associated with UE 101-1, such as a microphone, headset, or thelike, and UE 101-1 may provide (e.g., via user plane traffic 109)captured audio information, such as encoded audio information based onthe user's speech, to DCS 103 for distribution to UEs 101-2 and 101-3.Similarly, a camera of UE 101-1 may capture video information, such asthe user's face, and UE 101-1 may provide (e.g., via user plane traffic109) the captured video information to DCS 103 for distribution to UEs101-2 and 101-3.

UEs may each present a respective conference user interface (“UI”) 111via a display screen, speaker, etc. For example, UE 101-1 may presentconference UI 111-1, UE 101-2 may present conference UI 111-2, and UE101-3 may present conference UI 111-3. Each respective conference UI 111may present video information, such as captured video from some or allUEs 101 involved in the conference. Each respective conference UI 111may present audio information, such as captured audio from some or allUEs 101 involved in the conference.

Situations may arise where one or more UEs 101 experience degradednetwork conditions that may affect the quality of the conference. Forexample, as shown in FIG. 2 , a network and/or traffic issue 202 mayaffect the quality of the conference with respect to UE 101-1. Networkand/or traffic issue 202 may include, for example, degraded wirelesscommunications between UE 101-1 and a base station of a RAN of awireless network, degraded wireless communications between UE 101-1 anda WiFi access point, network congestion associated with a base stationor access point to which UE 101-1 is connected, and/or other issues thataffect the ability of UE 101-1 to output conference information (e.g.,user plane traffic such as audio and/or video) to DCS 103 via network105.

UE 101-1 may identify (at 204) the network and/or traffic issue bydetermining that a network throughput associated with communicationsbetween UE 101-1 and DCS 103 is below a threshold throughput, bydetermining that latency of communications between UE 101-1 and DCS 103is above a threshold latency, by determining that a quantity ofacknowledgement messages from DCS 103 over a given time period is belowa threshold quantity, by determining that a wireless signal strength orquality between UE 101-1 and a base station or access point is below athreshold signal strength or quality, and/or using some other suitablemanner of detecting network and/or traffic issue 202. In someembodiments, DCS 103 and/or some other device or system may detectnetwork and/or traffic issue 202, and notify UE 101-1 of the existenceof network and/or traffic issue 202. In some embodiments, UE 101-1 maypresent (e.g., via conference UI 111-1) an alert, such as visual alert201 and/or an audible alert, indicating that network and/or trafficissue 202 has been identified.

Based on detecting network and/or traffic issue 202 (e.g., in a mannerdiscussed above or some other suitable manner), UE 101-1 may generatecondensed conference information based on audio and/or video informationcaptured by UE 101-1. For example, UE 101-1 may, after identifyingnetwork and/or traffic issue 202, commence generating a transcript ofaudio data captured by an audio input device of UE 101-1. For example,UE 101-1 may use speech-to-text techniques to generate the transcript.In some embodiments, UE 101-1 may further condense the transcript, suchas by removing vowels, encoding words and/or phrases into a reduced setof characters, and/or may perform other operations to further condensethe transcript.

In some embodiments, UE 101-1 may generate a text-based description orset of annotations based on video information captured by a cameraassociated with UE 101-1. In some embodiments, UE 101-1 may utilizeimage recognition techniques, feature extraction techniques, and/orother suitable techniques to identify or classify video informationcaptured by the camera of UE 101-1. For example, UE 101-1 may identifythat a user of UE 101-1 has nodded his or her head, is smiling, hasstepped out of frame, and/or has performed other actions, and maygenerate condensed conference information indicating such identifiedactions.

In some embodiments, the condensed conference information may includeanimatronic control information for an animated simulation of the useror the user's face. For example, the animatronic control information mayinclude indications of reference points of the user's face (e.g., thetip of the user's nose, the user's eyes, the user's chin, etc.), as wellas movement information (e.g., position, roll, pitch, yaw, etc.)associated with the reference points. In this manner, DCS 103 may beable to generate (e.g., at 208, as discussed below) a detailedsimulation or recreation of the user's face.

While some examples of condensed conference information are describedabove, in some embodiments, UE 101-1 may generate other types ofcondensed conference information based on image, video, and/or otherinformation captured or sensed by UE 101-1. For example, animatroniccontrol information is discussed above in the context of a user's face.In practice, animatronic control information may be generated and/orused for other objects depicted in video captured by UE 101-1. Further,other types of control information or annotations may be generated, suchas control information or annotations regarding the user's speech,voice, etc. For instance, such control information may includeindications of head movement, facial expressions, or the like. In oneexample, an annotation such as “cough” may cause DCS 103 to generate(e.g., at 208, as discussed below) an animation of the user coughing,and/or may generate a coughing sound as part of reconstructed and/orextrapolated conference information.

In some embodiments, UE 101-1 may generate the condensed conferenceinformation when no network and/or traffic issue 202 is present, and maydiscard or otherwise not use the condensed conference information insituations where no network and/or traffic issue 202 is present. In someembodiments, transcripts and/or other information that may be used ascondensed conference information may be used by UE 101-1 and/or someother device or system to generate or modify a model associated with UE101-1 and/or a user of UE 101-1, such as a model that identifies speechpatterns or other attributes of the user of UE 101-1 and/or of UE 101-1itself. Such model may be used when generating reconstructed and/orextrapolated conference information, as described below.

UE 101-1 may provide (at 206) the condensed conference information toDCS 103. For example, UE 101-1 may provide such condensed conferenceinformation on a periodic basis, an intermittent basis, an event-drivenbasis, and/or on some other ongoing basis. For example, UE 101-1 mayprovide the condensed conference information every 3 seconds, everysecond, multiple times a second, and/or some other periodic orintermittent basis. In some embodiments, UE 101-1 may provide thecondensed conference information when detecting that a user of UE 101-1has spoken a complete sentence, phrase, or word. In some embodiments, UE101-1 may provide the condensed conference information when detectingthat a user of UE 101-1 has moved his or her head and/or has changed hisor her facial expression. In this manner, DCS 103 may receive thecondensed conference information in real time or near-real time, and mayfurther receive the condensed conference information at times thatcorrespond to audible or visual cues associated with the user. In someembodiments, UE 101-1 may provide an indication to DCS 103 of theexistence of network and/or traffic issue 202, based on which DCS 103may determine that UE 101-1 will be sending condensed conferenceinformation, and/or which may trigger a generation (e.g., at 208, asdiscussed below) of reconstructed and/or extrapolated conferenceinformation based on the condensed conference information.

In some embodiments, the condensed conference information may beprovided via control signaling 107. For example, UE 101-1 may, based onidentifying (at 204) network and/or traffic issue 202, and/or based ongenerating (at 204) the condensed conference information, provide (at206) the condensed conference information via SIP messages (e.g., SIPREINVITE and/or other SIP messages), keep-alive or “heartbeat” messages,null control messages, and/or other control signaling 107. As notedabove, control signaling 107 may be associated with QoS parametersand/or channels that receive QoS treatment that is different from userplane traffic 109. Such QoS treatment may include prioritizing controlsignaling 107 over user plane traffic 109, and/or guaranteeing orattempting to achieve (e.g., by network elements of network 105 and/orone or more other networks) less than a threshold latency for controlsignaling 107.

DCS 103 may generate (at 208) reconstructed and/or extrapolatedconference information based on the received (at 206) condensedconference information. For example, DCS 103 may utilize text-to-speechtechniques to generate or simulate audible speech based on a texttranscript of speech of a user of UE 101-1. Additionally, oralternatively, DCS 103 may utilize animation techniques or othersuitable techniques to generate or simulate movements, facialexpressions, or the like on a video simulation or animation of the userof UE 101-1, based on a text description or encoded information (e.g.,as included in the condensed conference information) indicating suchmovements, facial expressions, etc.). In some embodiments, a textdescription or annotations indicating detected movements, facialexpressions, or the like may be provided to other conferenceparticipants in addition to, or in lieu of, animations depicting suchmovements, facial expressions, or the like.

In some embodiments, DCS 103 may utilize a generic voice and/orsimulated face or head for the user. In some embodiments, DCS 103 mayutilize one or more models based on the user's voice, face, actions,etc. to generate custom-tailored reconstructed and/or extrapolatedconference information, based on particular attributes of the user. Inthis manner, different users may be simulated differently, and moreclosely to how such users actually sound and behave.

For example, as shown in FIG. 3 , DCS 103 may generate and/or refine (at302) a set of models 301 associated with UE 101-1, based on user planetraffic 109 sent to and/or received from UE 101-1. For example, UE 101-1may send and/or receive user plane traffic 109 in connection withparticipating in conferences with other UEs 101. Over time, DCS 103 maygenerate and/or refine models 301 based on audio information, videoinformation, text information, and/or other information received from UE101-1 and/or one or more other sources that generate or provideinformation associated with UE 101-1. In some embodiments, DCS 103 mayutilize artificial intelligence/machine learning (“AI/ML”) techniques orother suitable techniques in order to generate and/or refine the models,and/or to analyze user plane traffic (e.g., audio and/or video data) toidentify attributes or features of such traffic.

While this example is provided in the context of UE 101-1, similarconcepts may apply other UEs 101 and/or other types of devices. Further,in some embodiments, models 301 may be generated and refined on aper-user basis, such that different users using the same UE 101 may beassociated with different sets of models 301.

Models 301 may include, for example, speech pattern models, voicemodels, facial pattern models, and/or other suitable models. Speechpattern models may indicate, for example, diction, audible mannerisms,talking speed, and/or other attributes of the content of a user'sspeech. Voice models may indicate, for example, pitch, tonality,loudness, and/or attributes of the form or sound of a user's speech.Facial pattern models may indicate, for example, facial expressions of auser, head movements of the user, and/or other attributes of how a useris visually depicted.

In some embodiments, DCS 103 may maintain correlation and/or affinityinformation between different models 301. For example, DCS 103 maymaintain information associating particular speech pattern models withparticular voice models and/or facial pattern models. For instance, aDCS 103 may maintain information indicating that when the user says theword “Wow,” the pitch of the user's voice typically increases, theloudness of the user's voice typically increases, and the user'seyebrows are typically raised. In the preceding example, the term“typically” is used to reflect an analysis that indicates that anaffinity or correlation between these example occurrences exceeds athreshold affinity or correlation.

As noted above, such models 301 may be used by DCS 103 when generating(at 208) reconstructed and/or extrapolated conference information basedon condensed conference information received from a given UE 101. Forexample, as shown in FIG. 4 , DCS 103 may receive (at 402) a texttranscript of speech captured at UE 101-1. As similarly discussed above,such text transcript may be received via a control channel (e.g., viacontrol signaling 107), based on an identification by UE 101-1 ofdegraded network conditions during a conference with one or more otherUEs 101. While this example is provided in the context of a texttranscript of speech captured at UE 101-1, similar concepts may apply toother types of condensed conference information discussed above.

DCS 103 may generate (at 404) reconstructed and/or extrapolated audioand/or video 401 based on the text transcript and models 301 associatedwith UE 101-1, and/or associated with the user of UE 101-1. For example,DCS 103 may generate or simulate audible speech based on words orphrases encoded in or otherwise included in the text transcript andfurther based on speech models, voice models, or the like associatedwith UE 101-1 and/or the user. In some embodiments, DCS 103 may generateor simulate an image of the user, and may further generate or simulatemovements, facial expressions, etc. associated with the user based oninformation included in the transcript and further based on facialpattern models or other suitable models 301 associated with the user.

As noted above, some or all of the functionality associated with DCS 103may be implemented by an edge computing facility, such as a MEC that isdeployed at or proximate to a base station of a RAN. Such edge computingfacilities may communicate with UEs 101 via relatively low-latencycommunications, and may further include powerful processingcapabilities, which may enable reconstructed and/or extrapolated audioand/or video 401 to be generated in real time or near-real time,relative to when UE 101-1 captures audio and/or video information basedon which reconstructed and/or extrapolated audio and/or video 401 isgenerated. DCS 103 may further distribute reconstructed and/orextrapolated audio and/or video 401 to one or more other conferenceparticipants (e.g., UEs 101), thus providing conference services in aseamless, uninterrupted manner, even in situations where UE 101-1experiences network issues that would otherwise disrupt the conference.

In some embodiments, one or more of the operations described above withrespect to DCS 103 may be performed by one or more UEs 101, such asparticipants in a conference with a particular UE 101 from whichcondensed conference information is received. For example, DCS 103 mayprovide condensed conference information to one or more UEs 101, whichmay themselves generate reconstructed and/or extrapolated conferenceinformation based on the condensed conference information.

Returning to FIG. 2 , DCS 103 may provide (at 210) reconstructed and/orextrapolated conference information (e.g., reconstructed and/orextrapolated audio and/or video 401) to UEs 101-2 and 101-3. UEs 101-2and 101-3 may present, via conference UIs 111-2 and 111-3, respectively,some or all of the reconstructed and/or extrapolated conferenceinformation associated with UE 101-1. For example, conference UIs 111-2and 111-3 may include display areas 203-2 and 203-3, respectively,depicting a simulated and/or generated face and/or voice of a user of UE101-1, where such face and/or voice of the user may be included in orbased on the reconstructed and/or extrapolated conference informationprovided (at 210) to UEs 101-2 and 101-3.

FIG. 5 illustrates an example process 500 for generating and providingcondensed conference information based on the detection of degradednetwork conditions. In some embodiments, some or all of process 500 maybe performed by UE 101. In some embodiments, one or more other devicesmay perform some or all of process 500 in concert with or in lieu of UE101, such as DCS 103.

As shown, process 500 may include participating (at 502) in a conferencewith one or more UEs 101. For example, as discussed above, a set of UEs101 may participate in an audio and/or video conference, which mayinclude providing, sending, etc. audio and/or video traffic (e.g., userplane traffic 109) to DCS 103 and/or some other device or system thatfacilitates audio and/or video conferencing. Participating in the audioand/or video conference may further include receiving audio and/or videotraffic (e.g., user plane traffic 109) from DCS 103 and/or some otherdevice or system that facilitates audio and/or video conferencing. Theaudio and/or video traffic provided by each UE 101 may include audioand/or video that has been captured at each respective UE 101 via amicrophone, camera, headset, or other suitable device.

Process 500 may further include detecting (at 504) degraded networkconditions. For example, UE 101 may detect, via a speed test, aconnection test, and/or some other sort of suitable technique, thatnetwork conditions between UE 101 and one or more networks 105 to whichUE 101 is connected (e.g., via which UE 101 communicates with DCS 103)have degraded below a threshold level. For example, UE 101 may identifythat throughput of traffic from UE 101 via network 105 has fallen belowa threshold throughput, that latency of traffic from UE 101 via network105 has risen above a threshold latency, and/or that network conditionshave otherwise degraded, to the extent that the transmission of capturedaudio and/or video from UE 101 via network 105 may potentially benegatively impacted. As noted above, UE 101 may detect the degradednetwork conditions, and/or some other device or system may detect thedegraded network conditions and indicate such detection to UE 101.

Process 500 may additionally include continuing (at 506) to captureaudio and/or video. For example, UE 101 that is experiencing thedegraded network conditions may continue to capture audio and/or videovia a microphone, camera, headset, etc. after the detection of thedegraded network conditions.

Process 500 may also include generating (at 508) condensed conferenceinformation based on the audio and/or video captured after the detectionof the degraded network conditions. As discussed above, the condensedconference information may include a text transcript of captured audio,animatronic control instructions based on captured video information,annotations, and/or other suitable condensed conference information.

In this sense, the audio and/or video captured and/or sent (at 502)prior to detecting (at 504) degraded network conditions may beconsidered as first audio and/or video, and the captured audio and/orvideo based on which the condensed conference information is generated(at 508) may be considered as second audio and/or video. That is, block502 may include the sending of first audio and/or video captured at UE101, and block 508 may include the generation of condensed conferenceinformation based on second audio and/or video captured at UE 101.

Process 500 may further include outputting (at 510) the condensedconference information. For example, UE 101 may provide, output, etc.the condensed conference information to DCS 103. In some embodiments, UE101 may provide, output, etc. the condensed conference information withdifferent QoS parameters than audio and/or video that is sent (at 502)as part of the conference. For example, UE 101 may output the condensedconference information as, or include condensed conference informationin, control signaling 107 and/or via one or more control plane channels.In some embodiments, the condensed conference information may beincluded as an information element in one or more control messages.

As discussed above, DCS 103 may generate reconstructed and/orextrapolated conference information based on the condensed conferenceinformation. For example, as discussed above, DCS 103 may generate audiobased on a text transcript included in the condensed conferenceinformation, video based on animatronic instructions, etc. As alsodiscussed above, DCS 103 may generate and/or maintain one or more modelsassociated with UE 101 and/or a user of UE 101, which may be used togenerate custom-tailored reconstructed and/or extrapolated conferenceinformation. For example, different UEs 101 and/or users may beassociated with different speech patterns, voices, mannerisms,movements, etc., which may be reflected by the reconstructed and/orextrapolated conference information generated based on the condensedconference information and particular models associated with suchdifferent UEs 101 and/or users.

As similarly noted above, blocks 506-510 may performed or repeatediteratively, such that condensed conference information may be providedin real time or near-real time, and further such that reconstructedand/or extrapolated conference information may be generated in real timeor near-real time and provided to other conference participant UEs 101.

Process 500 may additionally include detecting (at 512) restoredconnection conditions. For example, UE 101 may identify that throughputof traffic from UE 101 via network 105 has risen above (or returned to)a threshold throughput, that latency of traffic from UE 101 via network105 has fallen below (or returned to) a threshold latency, and/or thatnetwork conditions have otherwise improved or been restored, to theextent that the transmission of captured audio and/or video from UE 101via network 105 is not likely to be negatively impacted. As noted above,UE 101 may detect the restored network conditions, and/or some otherdevice or system may detect the restored network conditions and indicatesuch detection to UE 101.

Process 500 may also include continuing (at 514) to capture audio and/orvideo at UE 101, and outputting (at 516) the captured audio and/orvideo. For example, based on the restored network connection conditions,UE 101 may provide, output, etc. the captured audio and/or video as userplane traffic 109, which may be distributed to one or more other UEs 101that are participants in the conference. In this manner, condensedconference information (e.g., not including captured video and/or audioinformation) may be sent by UE 101 when network conditions are below athreshold level, while full video and/or audio information may be sentby UE 101 when network conditions are at or above the threshold level.

FIG. 6 illustrates an example environment 600, in which one or moreembodiments may be implemented. In some embodiments, environment 600 maycorrespond to a Fifth Generation (“5G”) network, and/or may includeelements of a 5G network. In some embodiments, environment 600 maycorrespond to a 5G Non-Standalone (“NSA”) architecture, in which a 5Gradio access technology (“RAT”) may be used in conjunction with one ormore other RATs (e.g., a Long-Term Evolution (“LTE”) RAT), and/or inwhich elements of a 5G core network may be implemented by, may becommunicatively coupled with, and/or may include elements of anothertype of core network (e.g., an evolved packet core (“EPC”)). As shown,environment 600 may include UE 101, RAN 610 (which may include one ormore Next Generation Node Bs (“gNBs”) 611), RAN 612 (which may includeone or more one or more evolved Node Bs (“eNBs”) 613), and variousnetwork functions such as Access and Mobility Management Function(“AMF”) 615, Mobility Management Entity (“MME”) 616, Serving Gateway(“SGW”) 617, Session Management Function (“SMF”)/Packet Data Network(“PDN”) Gateway (“PGW”)-Control plane function (“PGW-C”) 620, PolicyControl Function (“PCF”)/Policy Charging and Rules Function (“PCRF”)625, Application Function (“AF”) 630, User Plane Function(“UPF”)/PGW-User plane function (“PGW-U”) 635, Home Subscriber Server(“HSS”)/Unified Data Management (“UDM”) 640, and Authentication ServerFunction (“AUSF”) 645. Environment 600 may also include one or morenetworks, such as Data Network (“DN”) 650. Environment 600 may includeone or more additional devices or systems communicatively coupled to oneor more networks (e.g., DN 650, RAN 610, and/or RAN 612), such as DCS103, which may perform one or more operations described above.

The example shown in FIG. 6 illustrates one instance of each networkcomponent or function (e.g., one instance of SMF/PGW-C 620, PCF/PCRF625, UPF/PGW-U 635, HSS/UDM 640, and/or AUSF 645). In practice,environment 600 may include multiple instances of such components orfunctions. For example, in some embodiments, environment 600 may includemultiple “slices” of a core network, where each slice includes adiscrete set of network functions (e.g., one slice may include a firstinstance of SMF/PGW-C 620, PCF/PCRF 625, UPF/PGW-U 635, HSS/UDM 640,and/or AUSF 645, while another slice may include a second instance ofSMF/PGW-C 620, PCF/PCRF 625, UPF/PGW-U 635, HSS/UDM 640, and/or AUSF645). The different slices may provide differentiated levels of service,such as service in accordance with different Quality of Service (“QoS”)parameters.

The quantity of devices and/or networks, illustrated in FIG. 6 , isprovided for explanatory purposes only. In practice, environment 600 mayinclude additional devices and/or networks, fewer devices and/ornetworks, different devices and/or networks, or differently arrangeddevices and/or networks than illustrated in FIG. 6 . For example, whilenot shown, environment 600 may include devices that facilitate or enablecommunication between various components shown in environment 600, suchas routers, modems, gateways, switches, hubs, etc. Alternatively, oradditionally, one or more of the devices of environment 600 may performone or more network functions described as being performed by anotherone or more of the devices of environment 600. Devices of environment600 may interconnect with each other and/or other devices via wiredconnections, wireless connections, or a combination of wired andwireless connections. In some implementations, one or more devices ofenvironment 600 may be physically integrated in, and/or may bephysically attached to, one or more other devices of environment 600.

UE 101 may include a computation and communication device, such as awireless mobile communication device that is capable of communicatingwith RAN 610, RAN 612, and/or DN 650. UE 101 may be, or may include, aradiotelephone, a personal communications system (“PCS”) terminal (e.g.,a device that combines a cellular radiotelephone with data processingand data communications capabilities), a personal digital assistant(“PDA”) (e.g., a device that may include a radiotelephone, a pager,Internet/intranet access, etc.), a smart phone, a laptop computer, atablet computer, a camera, a personal gaming system, an IoT device(e.g., a sensor, a smart home appliance, or the like), a wearabledevice, an Internet of Things (“IoT”) device, a Machine-to-Machine(“M2M”) device, or another type of mobile computation and communicationdevice. UE 101 may send traffic to and/or receive traffic (e.g., userplane traffic) from DN 650 via RAN 610, RAN 612, and/or UPF/PGW-U 635.

RAN 610 may be, or may include, a 5G RAN that includes one or more basestations (e.g., one or more gNBs 611), via which UE 101 may communicatewith one or more other elements of environment 600. UE 101 maycommunicate with RAN 610 via an air interface (e.g., as provided by gNB611). For instance, RAN 610 may receive traffic (e.g., voice calltraffic, data traffic, messaging traffic, signaling traffic, etc.) fromUE 101 via the air interface, and may communicate the traffic toUPF/PGW-U 635, and/or one or more other devices or networks. Similarly,RAN 610 may receive traffic intended for UE 101 (e.g., from UPF/PGW-U635, AMF 615, and/or one or more other devices or networks) and maycommunicate the traffic to UE 101 via the air interface.

RAN 612 may be, or may include, a LTE RAN that includes one or more basestations (e.g., one or more eNBs 613), via which UE 101 may communicatewith one or more other elements of environment 600. UE 101 maycommunicate with RAN 612 via an air interface (e.g., as provided by eNB613). For instance, RAN 610 may receive traffic (e.g., voice calltraffic, data traffic, messaging traffic, signaling traffic, etc.) fromUE 101 via the air interface, and may communicate the traffic toUPF/PGW-U 635, and/or one or more other devices or networks. Similarly,RAN 610 may receive traffic intended for UE 101 (e.g., from UPF/PGW-U635, SGW 617, and/or one or more other devices or networks) and maycommunicate the traffic to UE 101 via the air interface.

AMF 615 may include one or more devices, systems, Virtualized NetworkFunctions (“VNFs”), etc., that perform operations to register UE 101with the 5G network, to establish bearer channels associated with asession with UE 101, to hand off UE 101 from the 5G network to anothernetwork, to hand off UE 101 from the other network to the 5G network,manage mobility of UE 101 between RANs 610 and/or gNBs 611, and/or toperform other operations. In some embodiments, the 5G network mayinclude multiple AMFs 615, which communicate with each other via the N14interface (denoted in FIG. 6 by the line marked “N14” originating andterminating at AMF 615).

MME 616 may include one or more devices, systems, VNFs, etc., thatperform operations to register UE 101 with the EPC, to establish bearerchannels associated with a session with UE 101, to hand off UE 101 fromthe EPC to another network, to hand off UE 101 from another network tothe EPC, manage mobility of UE 101 between RANs 612 and/or eNBs 613,and/or to perform other operations.

SGW 617 may include one or more devices, systems, VNFs, etc., thataggregate traffic received from one or more eNBs 613 and send theaggregated traffic to an external network or device via UPF/PGW-U 635.Additionally, SGW 617 may aggregate traffic received from one or moreUPF/PGW-Us 635 and may send the aggregated traffic to one or more eNBs613. SGW 617 may operate as an anchor for the user plane duringinter-eNB handovers and as an anchor for mobility between differenttelecommunication networks or RANs (e.g., RANs 610 and 612).

SMF/PGW-C 620 may include one or more devices, systems, VNFs, etc., thatgather, process, store, and/or provide information in a manner describedherein. SMF/PGW-C 620 may, for example, facilitate the establishment ofcommunication sessions on behalf of UE 101. In some embodiments, theestablishment of communications sessions may be performed in accordancewith one or more policies provided by PCF/PCRF 625.

PCF/PCRF 625 may include one or more devices, systems, VNFs, etc., thataggregate information to and from the 5G network and/or other sources.PCF/PCRF 625 may receive information regarding policies and/orsubscriptions from one or more sources, such as subscriber databasesand/or from one or more users (such as, for example, an administratorassociated with PCF/PCRF 625).

AF 630 may include one or more devices, systems, VNFs, etc., thatreceive, store, and/or provide information that may be used indetermining parameters (e.g., quality of service parameters, chargingparameters, or the like) for certain applications.

UPF/PGW-U 635 may include one or more devices, systems, VNFs, etc., thatreceive, store, and/or provide data (e.g., user plane data). Forexample, UPF/PGW-U 635 may receive user plane data (e.g., voice calltraffic, data traffic, etc.), destined for UE 101, from DN 650, and mayforward the user plane data toward UE 101 (e.g., via RAN 610, SMF/PGW-C620, and/or one or more other devices). In some embodiments, multipleUPFs 635 may be deployed (e.g., in different geographical locations),and the delivery of content to UE 101 may be coordinated via the N9interface (e.g., as denoted in FIG. 6 by the line marked “N9”originating and terminating at UPF/PGW-U 635). Similarly, UPF/PGW-U 635may receive traffic from UE 101 (e.g., via RAN 610, SMF/PGW-C 620,and/or one or more other devices), and may forward the traffic toward DN650. In some embodiments, UPF/PGW-U 635 may communicate (e.g., via theN4 interface) with SMF/PGW-C 620, regarding user plane data processed byUPF/PGW-U 635.

HSS/UDM 640 and AUSF 645 may include one or more devices, systems, VNFs,etc., that manage, update, and/or store, in one or more memory devicesassociated with AUSF 645 and/or HSS/UDM 640, profile informationassociated with a subscriber. AUSF 645 and/or HSS/UDM 640 may performauthentication, authorization, and/or accounting operations associatedwith the subscriber and/or a communication session with UE 101.

DN 650 may include one or more wired and/or wireless networks. Forexample, DN 650 may include an Internet Protocol (“IP”)-based PDN, awide area network (“WAN”) such as the Internet, a private enterprisenetwork, and/or one or more other networks. UE 101 may communicate,through DN 650, with data servers, other UEs 101, and/or to otherservers or applications that are coupled to DN 650. DN 650 may beconnected to one or more other networks, such as a public switchedtelephone network (“PSTN”), a public land mobile network (“PLMN”),and/or another network. DN 650 may be connected to one or more devices,such as content providers, applications, web servers, and/or otherdevices, with which UE 101 may communicate.

FIG. 7 illustrates an example Distributed Unit (“DU”) network 700, whichmay be included in and/or implemented by one or more RANs (e.g., RAN610, RAN 612, or some other RAN). In some embodiments, a particular RANmay include one DU network 700. In some embodiments, a particular RANmay include multiple DU networks 700. In some embodiments, DU network700 may correspond to a particular gNB 611 of a 5G RAN (e.g., RAN 610).In some embodiments, DU network 700 may correspond to multiple gNBs 611.In some embodiments, DU network 700 may correspond to one or more othertypes of base stations of one or more other types of RANs. As shown, DUnetwork 700 may include Central Unit (“CU”) 705, one or more DistributedUnits (“DUs”) 703-1 through 703-N (referred to individually as “DU 703,”or collectively as “DUs 703”), and one or more Radio Units (“RUs”) 701-1through 701-M (referred to individually as “RU 701,” or collectively as“RUs 701”).

CU 705 may communicate with a core of a wireless network (e.g., maycommunicate with one or more of the devices or systems described abovewith respect to FIG. 6 , such as AMF 615 and/or UPF/PGW-U 635). In theuplink direction (e.g., for traffic from UEs 101 to a core network), CU705 may aggregate traffic from DUs 703, and forward the aggregatedtraffic to the core network. In some embodiments, CU 705 may receivetraffic according to a given protocol (e.g., Radio Link Control (“RLC”))from DUs 703, and may perform higher-layer processing (e.g., mayaggregate/process RLC packets and generate Packet Data ConvergenceProtocol (“PDCP”) packets based on the RLC packets) on the trafficreceived from DUs 703.

In accordance with some embodiments, CU 705 may receive downlink traffic(e.g., traffic from the core network) for a particular UE 101, and maydetermine which DU(s) 703 should receive the downlink traffic. DU 703may include one or more devices that transmit traffic between a corenetwork (e.g., via CU 705) and UE 101 (e.g., via a respective RU 701).DU 703 may, for example, receive traffic from RU 701 at a first layer(e.g., physical (“PHY”) layer traffic, or lower PHY layer traffic), andmay process/aggregate the traffic to a second layer (e.g., upper PHYand/or RLC). DU 703 may receive traffic from CU 705 at the second layer,may process the traffic to the first layer, and provide the processedtraffic to a respective RU 701 for transmission to UE 101.

RU 701 may include hardware circuitry (e.g., one or more RFtransceivers, antennas, radios, and/or other suitable hardware) tocommunicate wirelessly (e.g., via an RF interface) with one or more UEs101, one or more other DUs 703 (e.g., via RUs 701 associated with DUs703), and/or any other suitable type of device. In the uplink direction,RU 701 may receive traffic from UE 101 and/or another DU 703 via the RFinterface and may provide the traffic to DU 703. In the downlinkdirection, RU 701 may receive traffic from DU 703, and may provide thetraffic to UE 101 and/or another DU 703.

RUs 701 may, in some embodiments, be communicatively coupled to one ormore MECs 707. For example, RU 701-1 may be communicatively coupled toMEC 707-1, RU 701-M may be communicatively coupled to MEC 707-M, DU703-1 may be communicatively coupled to MEC 707-2, DU 703-N may becommunicatively coupled to MEC 707-N, CU 705 may be communicativelycoupled to MEC 707-3, and so on. MECs 707 may include hardware resources(e.g., configurable or provisionable hardware resources) that may beconfigured to provide services and/or otherwise process traffic toand/or from UE 101, via a respective RU 701.

For example, RU 701-1 may route some traffic, from UE 101, to MEC 707-1instead of to a core network (e.g., via DU 703 and CU 705). MEC 707-1may process the traffic, perform one or more computations based on thereceived traffic, and may provide traffic to UE 101 via RU 701-1. Inthis manner, ultra-low latency services may be provided to UE 101, astraffic does not need to traverse DU 703, CU 705, and an interveningbackhaul network between DU network 700 and the core network. In someembodiments, one or more MECs 707 may include, and/or may implement,some or all of the functionality described above with respect to DCS103.

FIG. 8 illustrates example components of device 800. One or more of thedevices described above may include one or more devices 800. Device 800may include bus 810, processor 820, memory 830, input component 840,output component 850, and communication interface 860. In anotherimplementation, device 800 may include additional, fewer, different, ordifferently arranged components.

Bus 810 may include one or more communication paths that permitcommunication among the components of device 800. Processor 820 mayinclude a processor, microprocessor, or processing logic that mayinterpret and execute instructions. In some embodiments, processor 820may be or may include one or more hardware processors. Memory 830 mayinclude any type of dynamic storage device that may store informationand instructions for execution by processor 820, and/or any type ofnon-volatile storage device that may store information for use byprocessor 820.

Input component 840 may include a mechanism that permits an operator toinput information to device 800 and/or other receives or detects inputfrom a source external to 840, such as a touchpad, a touchscreen, akeyboard, a keypad, a button, a switch, a microphone or other audioinput component, etc. In some embodiments, input component 840 mayinclude, or may be communicatively coupled to, one or more sensors, suchas a motion sensor (e.g., which may be or may include a gyroscope,accelerometer, or the like), a location sensor (e.g., a GlobalPositioning System (“GPS”)-based location sensor or some other suitabletype of location sensor or location determination component), athermometer, a barometer, and/or some other type of sensor. Outputcomponent 850 may include a mechanism that outputs information to theoperator, such as a display, a speaker, one or more light emittingdiodes (“LEDs”), etc.

Communication interface 860 may include any transceiver-like mechanismthat enables device 800 to communicate with other devices and/orsystems. For example, communication interface 860 may include anEthernet interface, an optical interface, a coaxial interface, or thelike. Communication interface 860 may include a wireless communicationdevice, such as an infrared (“IR”) receiver, a Bluetooth® radio, or thelike. The wireless communication device may be coupled to an externaldevice, such as a remote control, a wireless keyboard, a mobiletelephone, etc. In some embodiments, device 800 may include more thanone communication interface 860. For instance, device 800 may include anoptical interface and an Ethernet interface.

Device 800 may perform certain operations relating to one or moreprocesses described above. Device 800 may perform these operations inresponse to processor 820 executing software instructions stored in acomputer-readable medium, such as memory 830. A computer-readable mediummay be defined as a non-transitory memory device. A memory device mayinclude space within a single physical memory device or spread acrossmultiple physical memory devices. The software instructions may be readinto memory 830 from another computer-readable medium or from anotherdevice. The software instructions stored in memory 830 may causeprocessor 820 to perform processes described herein. Alternatively,hardwired circuitry may be used in place of or in combination withsoftware instructions to implement processes described herein. Thus,implementations described herein are not limited to any specificcombination of hardware circuitry and software.

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit thepossible implementations to the precise form disclosed. Modificationsand variations are possible in light of the above disclosure or may beacquired from practice of the implementations.

For example, while series of blocks and/or signals have been describedabove (e.g., with regard to FIGS. 1-5 ), the order of the blocks and/orsignals may be modified in other implementations. Further, non-dependentblocks and/or signals may be performed in parallel. Additionally, whilethe figures have been described in the context of particular devicesperforming particular acts, in practice, one or more other devices mayperform some or all of these acts in lieu of, or in addition to, theabove-mentioned devices.

The actual software code or specialized control hardware used toimplement an embodiment is not limiting of the embodiment. Thus, theoperation and behavior of the embodiment has been described withoutreference to the specific software code, it being understood thatsoftware and control hardware may be designed based on the descriptionherein.

In the preceding specification, various example embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of the possible implementations. Infact, many of these features may be combined in ways not specificallyrecited in the claims and/or disclosed in the specification. Althougheach dependent claim listed below may directly depend on only one otherclaim, the disclosure of the possible implementations includes eachdependent claim in combination with every other claim in the claim set.

Further, while certain connections or devices are shown, in practice,additional, fewer, or different, connections or devices may be used.Furthermore, while various devices and networks are shown separately, inpractice, the functionality of multiple devices may be performed by asingle device, or the functionality of one device may be performed bymultiple devices. Further, multiple ones of the illustrated networks maybe included in a single network, or a particular network may includemultiple networks. Further, while some devices are shown ascommunicating with a network, some such devices may be incorporated, inwhole or in part, as a part of the network.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, groups or other entities, itshould be understood that such information shall be used in accordancewith all applicable laws concerning protection of personal information.Additionally, the collection, storage, and use of such information canbe subject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as can be appropriatefor the situation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various access control,encryption and anonymization techniques for particularly sensitiveinformation.

No element, act, or instruction used in the present application shouldbe construed as critical or essential unless explicitly described assuch. An instance of the use of the term “and,” as used herein, does notnecessarily preclude the interpretation that the phrase “and/or” wasintended in that instance. Similarly, an instance of the use of the term“or,” as used herein, does not necessarily preclude the interpretationthat the phrase “and/or” was intended in that instance. Also, as usedherein, the article “a” is intended to include one or more items, andmay be used interchangeably with the phrase “one or more.” Where onlyone item is intended, the terms “one,” “single,” “only,” or similarlanguage is used. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processorsconfigured to: provide first audio or video, captured by the device, toone or more other devices via a network, wherein providing the capturedfirst audio or video includes outputting the captured first audio orvideo as user plane traffic via the network; detect a degradation of aconnection between the device and the network; generate condensedconference information based on second audio or video captured by thedevice after determining the degradation of the connection, whereingenerating the condensed conference information includes at least oneof: generating a text transcript based on particular captured audioinformation included in the second audio or video information, oridentifying movements depicted in particular captured video informationincluded in the second audio information and generating animatroniccontrol instructions based on the identified movements; and output thecondensed conference information via the network, in lieu of outputtingthe second audio or video information via the network, whereinoutputting the condensed conference information includes outputting thecondensed conference information as control plane signaling via thenetwork.
 2. The device of claim 1, wherein a conference system receivesthe condensed conference information, generates reconstructed conferenceinformation based on the condensed conference information, and providesthe reconstructed conference information to the one or more otherdevices.
 3. The device of claim 2, wherein the conference system isimplemented at a Multi-Access/Mobile Edge Computing (“MEC”) deviceassociated with the network.
 4. The device of claim 1, whereingenerating the condensed conference information includes: generating thetext transcript based on the particular captured audio information; andgenerating the animatronic control instructions based on the identifiedmovements depicted in the particular captured video information.
 5. Thedevice of claim 1, wherein a conference system receives the animatroniccontrol instructions, generates one or more animations based on theanimatronic control instructions, and provides the one or moreanimations to the one or more other devices.
 6. A non-transitorycomputer-readable medium, storing a plurality of processor-executableinstructions to: provide first audio or video, captured by a device, toone or more other devices via a network, wherein providing the capturedfirst audio or video includes outputting the captured first audio orvideo as user plane traffic via the network; detect a degradation of aconnection between the device and the network; generate condensedconference information based on second audio or video captured by thedevice after determining the degradation of the connection, whereingenerating the condensed conference information includes at least oneof: generating a text transcript based on particular captured audioinformation included in the second audio or video information, oridentifying movements depicted in particular captured video informationincluded in the second audio information and generating animatroniccontrol instructions based on the identified movements; and output thecondensed conference information via the network, in lieu of outputtingthe second audio or video information via the network, whereinoutputting the condensed conference information includes outputting thecondensed conference information as control plane signaling via thenetwork.
 7. The non-transitory computer-readable medium of claim 6,wherein a conference system receives the condensed conferenceinformation, generates reconstructed conference information based on thecondensed conference information, and provides the reconstructedconference information to the one or more other devices.
 8. Thenon-transitory computer-readable medium of claim 7, wherein theconference system is implemented at a Multi-Access/Mobile Edge Computing(“MEC”) device associated with the network.
 9. The non-transitorycomputer-readable medium of claim 6, wherein generating the condensedconference information includes: generating the text transcript based onthe particular captured audio information; and generating theanimatronic control instructions based on the identified movementsdepicted in the particular captured video information.
 10. Thenon-transitory computer-readable medium of claim 6, wherein a conferencesystem receives the animatronic control instructions, generates one ormore animations based on the animatronic control instructions, andprovides the one or more animations to the one or more other devices.11. A method, comprising: providing, by a device, first audio or video,captured by the device, to one or more other devices via a network,wherein providing the captured first audio or video includes outputtingthe captured first audio or video as user plane traffic via the network;detecting a degradation of a connection between the device and thenetwork; generating condensed conference information based on secondaudio or video captured by the device after determining the degradationof the connection, wherein generating the condensed conferenceinformation includes at least one of: generating a text transcript basedon particular captured audio information included in the second audio orvideo information, or identifying movements depicted in particularcaptured video information included in the second audio information andgenerating animatronic control instructions based on the identifiedmovements; and outputting the condensed conference information via thenetwork, in lieu of outputting the second audio or video information viathe network, wherein outputting the condensed conference informationincludes outputting the condensed conference information as controlplane signaling via the network.
 12. The method of claim 11, wherein aconference system receives the condensed conference information,generates reconstructed conference information based on the condensedconference information, and provides the reconstructed conferenceinformation to the one or more other devices.
 13. The method of claim11, wherein generating the condensed conference information includes:generating the text transcript based on the particular captured audioinformation; and generating the animatronic control instructions basedon the identified movements depicted in the particular captured videoinformation.
 14. The method of claim 11, wherein a conference systemreceives the animatronic control instructions, generates one or moreanimations based on the animatronic control instructions, and providesthe one or more animations to the one or more other devices.
 15. Themethod of claim 11, wherein the user plane traffic is associated with afirst set of Quality of Service (“QoS”) parameters, and wherein thecontrol plane signaling is associated with a different second set of QoSparameters.
 16. The device of claim 1, wherein the user plane traffic isassociated with a first set of Quality of Service (“QoS”) parameters,and wherein the control plane signaling is associated with a differentsecond set of QoS parameters.
 17. The non-transitory computer-readablemedium of claim 6, wherein the user plane traffic is associated with afirst set of Quality of Service (“QoS”) parameters, and wherein thecontrol plane signaling is associated with a different second set of QoSparameters.
 18. The non-transitory computer-readable medium of claim 6,wherein outputting the condensed conference information as control planesignaling via the network includes outputting the condensed conferenceinformation as an information element in one or more control messages.19. The device of claim 1, wherein outputting the condensed conferenceinformation as control plane signaling via the network includesoutputting the condensed conference information as an informationelement in one or more control messages.
 20. The method of claim 11,wherein outputting the condensed conference information as control planesignaling via the network includes outputting the condensed conferenceinformation as an information element in one or more control messages.